๐ฌค rns.recipes
top
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ RNS 1.5.0 Released โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Started by Mark ยท 29d ago ยท 8dd57a7382268096
Page 1 of 2
[ 1 ] Next >
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-1
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Mark #1 โ
โ 8dd57a7382268096 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
Ready to grab over RNS itself or pip
a8d24177d946de4f1f0a0fe1af9a1338:/page/release.mu`g=reticulum|r=reticulum|t=1.5.0
This release significantly improves the core Transport handling of RNS, with a
priority-based ingress queue backend, substantially improved efficiency of both data and
management traffic handling, more efficient ingress/egress limiting, and a long list of
other improvements and bugfixes.
Changes
โข Added ability to include operator LXMF address in interface discovery information
โข Added prioritized inbound traffic processing to the transport core
โข Added configurable inbound queue lengths for data, announce, path request and ingress
limited traffic
โข Added early filtering for inbound traffic and improved filtering performance
โข Added per-interface protocol violation tracking
โข Added in-flight path requests tracking
โข Added request and response batching for in-flight path requests
โข Added ability to signal blackholed status in announce validation return to the API
โข Added full link MDU utilization for `Channel` and `Buffer`
โข Added inbound queue pressure and queue drop statistics to `rnstatus`
โข Added detailed announce and path request traffic flow statistics per interface to
`rnstatus`
โข Added total announce and PR count/frequency stats per interface to `rnstatus`
โข Added data flow speed and composition stats to `rnstatus`
โข Added protocol violation stats to `rnstatus`
โข Added active link statistics to `rnstatus`
โข Added blocked IP listings to `rnstatus`
โข Added medium bitrate based timeout calculation helpers and RPC functions, by
Zenith
โข Added extra timeout for discovery path requests when slow interfaces are online, by
Zenith
โข Added adaptive timeouts to `rncp`, `rnpath`, `rnprobe` and `rnx`, by
Zenith
โข Added adaptive timeout calculation to `rngit`, by Zenith
โข Improved overall Transport inbound processing speed
โข Improved path request handling significantly
โข Improved path request ingress limiting and accounting
โข Improved egress limiting responsiveness under high incoming path request load
โข Improved transport background job processing
โข Improved early rejection of packets with excessive hop counts
โข Fixed `BackboneInterface` EPOLL receive starvation and ingress control timestamp
handling, by JRG
โข Fixed potential transport deadlock on receipts lock when callbacks sends packets, by
JRG
โข Fixed transport state handling edge cases in path request, announce queue and pending
link processing, by JRG
โข Fixed link watchdog not resetting on receive exceptions, by JRG
โข Fixed `Resource` cancellation on multi-segment resources, by JRG
โข Fixed `Resource` transfer part index alignment and rebinding, by JRG
โข Fixed stale BLE device reference in `RNodeInterface`, by JRG
โข Fixed ratchet cleaning retained preservation, by JRG
โข Fixed invalid `rnstatus` statistics handling, by JRG
โข Fixed various bugs in packet, link and interface handling, by JRG
โข Fixed per-interface burst count inconsistencies in `rnstatus` output
โข Fixed `rngit` file resource operations failing on Windows
โข Fixed `rnodeconf` config summary incorrectly displaying WiFi mode
โข Fixed speedtest example aborting transfers on stale link status
โข Updated documentation, including manual sections on queue tuning and interface
discovery options
Enjoy!
โ 19 โ 0 โค 19
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-2
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ joakim #2 โ
โ b918e659eeedac9a โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
That was quick!
โ 2 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-3
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Anonymous #3 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
Is the manual available as a nomad page? I can't see any manuals for 1.5.0 online
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-4
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Anonymous #4 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
1.5.0 worked on our local mesh, whereas 1.4.2 was dropping connections. Thanks for the
release and all who contributed.
โ 1 โ 0 โค 1
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-5
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ joakim #5 โ
โ b918e659eeedac9a โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
Looks to be running fine on my transport node. I don't notice anything except things
running smoothly, and that's the sign of good work. Appreciate all the work that went
into this!
โ 3 โ 0 โค 2
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-6
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ aetherlab #6 โ
โ 509723a0ccb60610 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
Thank you Mark, updated all rns.sofia network devices. Looks good for now!
I hope we will see 1.5.0 in Sideband soon.
Best of the best!
โ 4 โ 1 โค 2
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-7
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Mark #7 โ
โ 8dd57a7382268096 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 29d ago
Thanks everyone, good to hear! If you find anything weird, post it over in the RNS 1.5.0
testing thread. This was a massive piece of work, and I've tried to be ultra careful
here, but if bugs snuck in, we'll get them fixed :)
Yes @aetherlab, I'll have an updated Sideband build soon including RNS 1.5.0 :)
-
Regarding the manual, you can always fetch the latest manual in PDF and EPUB formats
directly using rngit :
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch "latest:Reticulum Manual.pdf"
Or download it using nomadnet from the latest release page:
a8d24177d946de4f1f0a0fe1af9a1338:/page/release.mu`g=reticulum|r=reticulum|t=latest
Or, there's also a fully nomadnet browsable version on Aleph:
a8d24177d946de4f1f0a0fe1af9a1338:/page/blob.mu`g=reticulum|r=reticulum|ref=HEAD|path=docs
/markdown/index.md
Or, if you clone the RNS repository, there's a static HTML version in there as well.
And, I've also pushed the latest manual to the reticulum.network website now, so it's
available on the web too now.
โ 7 โ 0 โค 9
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-8
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Anonymous #8 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 28d ago
Would you mind talking a bit about how the ingress queue works? In the manual it says:
โ If an inbound packet arrives and its target queue is full, the packet is dropped.
Naturally I dont want packets to be dropped at all if they are legitimate, but now I
worry they might be ^^ what does the queue lenght mean in practice when running a public
backbone node for example? I am not competent enough to figure this out from the code.
โ 1 โ 0 โค 1
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-9
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Mark #9 โ
โ 8dd57a7382268096 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 28d ago
By default, there's four queues. In prioritized order:
โข Data (highest priority)
โข Announces
โข Path requests
โข Ingress limited traffic (lowest priority)
If your system can't keep up with transporting packets as fast as they're arriving (for
example, if it is at 100% CPU utilization), something will have to get dropped. You want
ingress limited traffic to get dropped first (PR and announce spam, for example, or bogus
data traffic from interfaces with many protocol violations). If dropping that is still
not enough to keep up, path requests are dropped, then announces, and only then is data
packets considered for dropping. The data queue is much larger than the other three by
default.
In almost all cases, you will never drop a legitimate packet. You can watch the queue
pressure and drop stats with rnstatus -qmI1 for example.
โ 0 โ 0 โค 3
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-10
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Mark #10 โ
โ 8dd57a7382268096 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 28d ago
This also serves to prioritize drainage by traffic class. For example, you don't want
your live voice call to cut out and go all wonky because some arsehole decides to connect
and dump 10k bogus path requests on your node in a second. The queues solve that :)
โ 1 โ 0 โค 2
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
[ 1 ] Next >
Page 1 of 2
โ INFO โ Identify to this node to post. How?
bottom